V318 - PROTAGONIST-OWNED SOLO CHECKPOINTS / OPEN ARBITRATION FROM OPTIONS
Base: V317. No changes to character data, combat/death, scripted pauses, cutscene
rules, account ownership, or native Import/Export.

NEW BUTTON
In-game OPTIONS (Escape) now has "CHARACTER ARBITRATION" on the upper left.
In a running multiplayer session, choose it to open the original BG2 character
arbitration engine. This is user-initiated, and does NOT set a persistent
join/leave arbitration event. Press the native Done/Play to return to gameplay.
The button is not usable during a cutscene or when all party members are dead.
It is available to both host and connected clients; the existing owner/player
permissions are not relaxed.

OWNER-ONLY CAMPAIGN CHECKPOINT
V317's protagonist Save Game is now available ONLY after character slots 2..6
are actually empty (no connected remote names, no arbitration character rows,
and no actor occupying a corresponding world party slot). This guarantees
that NEW V318 checkpoints cannot knowingly serialize the party's guest
characters. The native engine still saves ALL game/area/quest state correctly.
V318 labels these new native save names with the 'SOLO_' suffix marker AFTER
account and campaign prefixes, for example:
  DRK09_drakhysys_SoA_SOLO_Campaign Progress
BG2 writes the full native save in its existing mpsave folder. The existing
characters/<Account>/campaign_progress/<Campaign>.json still only indexes
native saves, not CHR or position backups. No account/character files are moved.

BEFORE SAVING
1. Have other players leave normally. The host can reopen Character Arbitration
   from Options to verify slot 2..6 are empty and permit existing leave cleanup.
2. Return to gameplay, open OPTIONS and Save Game while Player 1 is alive.
3. To resume later, choose the account/campaign's RESUME CAMPAIGN and select
   the tagged SOLO_ save. Guests may subsequently join the active host world.

NOTE ON OLD SAVES
Existing V317 native saves remain untouched and selectable, but might contain
other player characters. For a guaranteed empty-guest checkpoint, create a new
SOLO_ save only AFTER the guest slots are actually empty. A client joining
another host does NOT load the client's own campaign location; they join the
protagonist's running campaign. Player account/campaign indices remain separate.

LIMITATIONS / TESTING
BG2 and EEex must still be tested with multiple actual game clients; static UI
and setup regression tests cannot prove engine multiplayer behavior. V318 does
not delete remote party members from a loaded save, force clients to leave for
saving, edit .GAM party data, or automatically create saves. The native engine
will continue to serialize any other populated party positions, which is why
protagonist-only Save is disabled until they are empty. This is a conservative
safety measure: it may disable saving until the host removes departed guest
characters in Arbitration. Preserve V317 as a fallback during live testing.

INSTALL
1. Close all BG2 windows.
2. Extract ZIP. Run All Editors/SETUP_IN_GAME_ACCOUNTS.bat.
3. Launch via InfinityLoader.exe with EEex.
